Systems and methods for establishing cloud-based instances with independent permissions

ABSTRACT

A method and system for facilitating management of cloud-based service instances, the system including one or more computing systems configured to communicate with at least one multi-tenant computing cloud, and configured to establish a cloud-based service instance hosted in the multi-tenant computing cloud and an access entity with permissions to access the established cloud-based service instance. The system can receive a request for the cloud-based service instance, the request authenticated as originating from a requestor; consult a set of access controls associated with the cloud-based service instance; determine, responsive to the consulting, if the request is allowable by the requestor; and enable, responsive to determining that the request is allowable by the requestor, the requestor to complete the request using a restricted access credential associated with the access entity.

CROSS REFERENCE TO RELATED APPLICATIONS

This Application claims priority to U.S. Patent Application No.61/786,948, titled “Systems and Methods for Establishing Cloud-BasedInstances with Independent Permissions,” filed Mar. 15, 2013, which isincorporated herein by reference.

BACKGROUND

The present disclosure relates generally to managing cloud-based virtualservers and service instances hosted by multi-tenant cloud computingservice providers. Multi-tenant cloud computing service providersgenerally allow a customer to instantiate virtual servers runningsoftware specified by the customer without requiring the customer to ownor manage the underlying hardware. Multi-tenant cloud computing serviceproviders may therefore be referred to as hosts or host providers. Hostsproviders include, for example, Amazon.com, Inc. (e.g., Amazon WebServices), Rackspace Hosting, Inc. (e.g., Rackspace Cloud), Google Inc.(e.g. Google Compute Engine), and Microsoft Corp. (e.g., Windows Azure).

SUMMARY

Aspects and embodiments of the present disclosure are directed tosystems and methods of facilitating management of cloud-based serviceinstances. In general, in some embodiments, a management system isconfigured to communicate with at least one multi-tenant computingcloud. The management system can establish a cloud-based serviceinstance hosted in the multi-tenant computing cloud and an access entitywith permissions to access the established cloud service instance. Themanagement system can receive a request for the cloud-based serviceinstance from an authenticatable requestor and consult a set of accesscontrols associated with the cloud-based service instance to determineif the request is allowable by the requestor. The management system canenable, or facilitate, an authorized authenticated request to themulti-tenant computing cloud using an access credential associated withthe access entity.

At least one aspect is directed to methods of facilitating management ofcloud-based service instances, the methods comprising establishing, by acloud management service configured to communicate with a multi-tenantcomputing cloud, a cloud-based service instance hosted in themulti-tenant computing cloud and an access entity with permissions toaccess the established cloud service instance; receiving, by the cloudmanagement service, a request for the cloud-based service instance, therequest authenticated as originating from a requestor; consulting, bythe cloud management service, a set of access controls associated withthe cloud-based service instance; determining, by the cloud managementservice, responsive to the consulting, if the request is allowable bythe requestor; and enabling, by the cloud management service responsiveto determining that the request is allowable by the requestor, therequestor to complete the request using an access credential associatedwith the access entity.

The methods may further include communicating, by the cloud managementservice, with the multi-tenant computing cloud, to create, start,instantiate, discover, identify, duplicate, import, configure, orgenerate, the cloud-based service instance. The methods may includestoring, by the cloud management service, the access credential for theaccess entity.

The methods may include returning, to the requestor, the accesscredential associated with the access entity, wherein the request is arequest for direct access, by the requestor, to the cloud-based serviceinstance. The methods may include forwarding the request to themulti-tenant computing cloud, with the access credential associated withthe access entity, wherein the request is a request to perform an actionon the cloud-based service instance. The method may include, prior toforwarding the request, converting the request from a first requeststructure, format, or language, into a second request structure, format,or language.

The methods may include creating a new access entity with a new accesscredential and configuring the access entity's permissions in themulti-tenant compute cloud such that the access entity only has accessto the cloud-based service instance being accessed by the requestor.

At least one aspect is directed to a system for facilitating managementof cloud-based service instances, the system comprising one or morecomputing systems configured to communicate with at least onemulti-tenant computing cloud, the one or more computing systemsconfigured to establish a cloud-based service instance hosted in themulti-tenant computing cloud and an access entity with permissions toaccess the established cloud service instance; receive a request for thecloud-based service instance, the request authenticated as originatingfrom a requestor; consult a set of access controls associated with thecloud-based service instance; determine, responsive to the consulting,if the request is allowable by the requestor; and enable, responsive todetermining that the request is allowable by the requestor, therequestor to complete the request using an access credential associatedwith the access entity.

The systems may be further configured to establish the cloud-basedservice instance by communicating with the multi-tenant computing cloudto create, start, instantiate, discover, identify, duplicate, import,configure, or generate, the cloud-based service instance. The systemsmay be further configured to store the access credential for the accessentity.

The systems may be further configured to return, to the requestor, theaccess credential associated with the access entity, wherein the requestis a request for direct access, by the requestor, to the cloud-basedservice instance. The systems may be further configured to forward therequest to the multi-tenant computing cloud, with the access credentialassociated with the access entity, wherein the request is a request toperform an action on the cloud-based service instance. The systems may,prior to forwarding the request, convert the request from a firstrequest structure, format, or language, into a second request structure,format, or language.

The systems may be further configured to create a new access entity witha new access credential and configuring the access entity's permissionsin the multi-tenant compute cloud such that the access entity only hasaccess to the cloud-based service instance being accessed by therequestor.

The cloud-based service instance may provide one of a database, a loadbalancer, a message queue, a communication channel, and data storage.The cloud-based service instance may be a virtual service provided inthe multi-tenant computing cloud. The access entity permissions may berestricted to only allow access to the established cloud serviceinstance. The cloud-based service instance may be associated with aresource pool comprising one or more cloud-based service instances andthe access entity permissions may be restricted to only accessingcloud-based service instances in the resource pool. The authenticatedrequest may be cryptographically signed by one or more of the requestor,an authentication service, and a third-party signing authority.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. Likereference numbers and designations in the various drawings indicate likeelements. For purposes of clarity, not every component may be labeled inevery drawing. In the drawings:

FIG. 1 is a block diagram illustrating an example network;

FIGS. 2A and 2B are block diagrams of a typical computer 200 useful asclient computing devices and server computing devices;

FIG. 3 is a flowchart for a method of facilitating management ofcloud-based service instances.

DETAILED DESCRIPTION

FIG. 1 is a block diagram illustrating an example environment includingthird-party multi-tenant computing clouds, virtual servers and servicesoperating in the computing clouds, and a cloud management service. Inbrief overview, a customer device 115 interacts with a cloud managementservice 110, or more simply “manager” 110. The manager 110 is designedto interact with multiple multi-tenant computing clouds 120 a-z, eachprovided by one of many possible cloud providers and managed via cloudcontrollers 124 a-z. Each cloud 120 hosts one or more virtual serversand hosted services 130. Communication between each participant isfacilitated by a communication channel, e.g., the customer device 115may communicate with the manager 110 via a channel 152 such as theInternet. The manager may communicate with a first cloud 120 a via aprivate dedicated channel 154 and communicate with other clouds 120 b-zvia another channel 156. In general, the cloud management service 110may communicate with a cloud controller 124 (e.g., to allocate ordeallocate a virtual server or service) and the cloud management service110 may communicate with virtual servers or services in a cloud 130. Insome embodiments, the customer device 115 may be enabled to communicatewith a virtual server or hosted service 130 via a direct channel 158,such as an encrypted secure tunnel operating over the Internet. Acustomer device 115 may communicate with virtual servers or services 130and, in some embodiments, with a cloud controller 124.

The multi-tenant cloud computing service providers generally provide acomputing platform, e.g., cloud controllers 124 a-z, that enables acustomer to instantiate and use one or more virtual servers in variousdifferent configurations matching the particular needs of the customer.A customer may configure, use, or manipulate these services and serversto meet the customer's needs. A customer may be an individual or anorganization, e.g., a corporate entity. Host providers typicallycharacterize a customer as an account, such that the servers andservices for a customer are scoped within a single account. A customermay have one or more users authorized for the account. In the generalcase, each user is represented by an access entity, which is a formalencoding of the user's identity, e.g., using an email address, a userID, an account ID, or some combination thereof. A user may provision,configure, or use the virtual servers and services hosted by themulti-tenant cloud computing service provider, e.g., by issuing requeststo the host provider. For example, the user may submit a request to acloud controller 124 a-z using a protocol such as HTTP or HTTPS. Thehost provider generally authenticates a request using a set of accesscredentials associated with an access entity submitting the request. Theauthentication may be performed by the cloud controller 124, acting as asort of gatekeeper. For example, a user may confirm an access entity bysupplying a username and password, e.g., at the beginning of anauthenticated session. Some host providers use key-id/secret-key pairsor public/private key pairs for authentication. An access entity mayhave multiple access credentials. For example, Amazon Web Servicesallows two key-id/secret-key pairs. Additionally, an account may havemultiple access entities. For example, Amazon Web Services allows alarge number of users to access an account via the Identity and AccessManagement (IAM) feature set. Typically, when a host provider supportsmultiple access entities per account, each access entity may havedifferent rights or permissions.

Multi-tenant cloud computing service host providers generally alsoenable a customer to launch various services related to the virtualservers and other services in the cloud. These services may be describedas virtual services or hosted services. As an example of such services,Amazon.com, Inc., provides the Amazon Elastic Compute Cloud (AmazonEC2), Amazon Simple Storage Service (Amazon S3), and Amazon RelationalDatabase Service (Amazon RDS). These hosted or virtual servicesgenerally relate to, and interact with, the virtual servers used by acustomer. For example, Amazon Elastic MapReduce (Amazon EMR) is a webservice that enables Amazon's customers to process large amounts ofdata. As Amazon.com, Inc., explains: “It [EMR] utilizes a hosted Hadoopframework running on the web-scale infrastructure of Amazon ElasticCompute Cloud (Amazon EC2) and Amazon Simple Storage Service (AmazonS3).” (http://aws.amazon.com/elasticmapreduce/).

There is a distinction between the services provided or hosted by a hostprovider and a particular instance of a service. That is, many virtualservices allow a user to create multiple instances of the service, whereeach instance provides the same type of functionality but independentlyfrom one another. For example, each “load balancer” (a virtual serviceinstance) in ELB (a virtual service) is configured independently andoperates independently of other load balancers. Similarly, each RDSdatabase instance is independent of other RDS instances, but they areall part of the RDS service. In the case of S3, each “bucket” representsa separate storage instance. Access to individual service instances canbe controlled.

Referring to FIG. 1 in greater detail, the manager 110 may comprise anycomputer device capable of interacting with one or more multi-tenantcomputing clouds 120 a-z and cloud controllers 124 a-z. The manager 110may comprise a single server, server cluster, or virtual servers (e.g.,cloud based servers). In some embodiments, the manager 110 may beoperated independently from the cloud service host providers, that is,the cloud management service 110 may interact with third-party clouds.In some embodiments, the manager 110 may have one or more associateddatabases for storing configuration information and/or virtual serverimages. The manager 110 may be communicatively connected to privatenetworks and/or public networks such as the Internet. The manager mayinclude a daemon running to monitor one or more servers or servicesoperating in a cloud. In some embodiments, the manager records the datagenerated by the daemon to a database, which may be local, operated onthe network, or provided by a cloud-based service.

Generally, the manager 110 is capable of interacting with a cloudprovider to set up a customer account and any access entities such as anadministrative entity, subscriber profile, or user identity. Whileaccess entities may have different names or descriptions in practiceacross different providers, they are referred to herein as an “accessentity” to avoid any confusion between an umbrella customer account andindividual users of a customer account. A subscriber may have multipleaccess entities with a single provider, for example, an access entityfor each of the subscriber's employees. Each access entity may have itsown associated authentication credentials. Each access entity may haveits own associated permissions or restrictions. For example, a customermay have an access entity authorized to make changes and a second accessentity only authorized for read-only operations.

Generally, the manager 110 is capable of interacting with a cloudprovider to instantiate cloud-based services and virtual servers hostedby the cloud. The interaction may be in the form of a request from themanager 110 to the cloud provider or to a service operated by the cloudprovider. The interaction may be in the form of steps performed by themanager 110. In some embodiments, the manager 110 is further capable ofmodifying an instantiated cloud-based service or virtual server, e.g.,pausing a service or updating a virtual server. In some embodiments, themanager 110 converts between a standardized instruction set andinstruction sets tailored to each cloud host.

The customer, or representatives of the customer, may access orcommunicate with the manager 110 via a customer device 115 over acommunication channel 152. The customer device 115 may be a server, avirtual machine, a desktop computer, a laptop computer, a mobilecomputing device, or any other computing platform from which a customeror customer agent may interact with the manager 110. The customer device115 or the manager 110 may also be virtual servers running in one of thevirtual compute clouds 120 a-z. The communication channel 152 may bewired or wireless. The communication channel 152 may operate over anintranet, a private network, a public network, or encrypted privatechannels over a public network. In some embodiments, the manager 110presents an API (Application Programming Interface) via thecommunication channel 152 to the customer device 115. In someembodiments, the interface presented by the manager 110 is a webinterface or website. In some embodiments, the customer device 115executes software configured to communicate with the manager 110.

Each cloud 120 is hosted by a cloud provider and directly managed by acloud controller 124. Each cloud 120 a-z may be a multi-tenant cloud,that is, each cloud host may sell cloud based services to multipleparties or tenants. Multi-tenant cloud computing service providersinclude, for example, Amazon.com, Inc. (e.g., Amazon Web Services),Rackspace Hosting, Inc. (e.g., Rackspace Cloud), Google Inc. (e.g.Google Compute Engine), and Microsoft Corp. (e.g., Windows Azure).Providers generally host servers and services that enable customers toinstantiate a number of virtual servers in a variety of differentconfigurations to match their needs and to launch various servicesrelated to the virtual servers. For example, Amazon.com, Inc., providesvirtual servers in the Amazon Elastic Compute Cloud (Amazon EC2), and itprovides services in Amazon Simple Storage Service (Amazon S3), AmazonElastic Load Balancer (ELB), Amazon Dynamo DB, and Amazon RelationalDatabase Service (Amazon RDS).

A cloud-based service 130 may be established by the cloud controller 124a or by the cloud manager 110. For example, a customer may access themanager 110, e.g., via device 115 and communication channel 152, andrequest that a service be established. The manager 110 coordinatesinstantiation of a cloud-based service 130 in a cloud 120 a. Thecustomer may then use the manager 110 to monitor the cloud-based serviceinstance 130 and to handle any other service oriented requests. In someembodiments, the manager 110 provides the customer device 115 with atoken or access entity credentials enabling the customer device 115 tocommunicate directly with the service 130, e.g., via communicationchannel 158.

The user device 115, manager 110, and clouds 120 a-z, may be connectedin any manner, and via any network or networks. The channels 152, 154,156, 158, illustrated in FIG. 1 may comprise the Internet, localnetworks, web servers, file servers, routers, databases, computers,servers, network appliances, or any other computing devices capable ofsending and receiving information. A network may comprise computingdevices connected via cables, infrared ports, wireless signals, or anyother means of connecting multiple computing devices. A network and anydevices connected to the networks may communicate via any communicationprotocol used to communicate among or within computing devices,including without limitation SSL, BitTorrent, HTML, XML, RDP, ICA, FTP,HTTP, SIP, XMPP (also known as Jabber), TCP, IP, UDP, IPX, SPX, NetBIOS,NetBEUI, SMB, SMTP, Ethernet, ARCNET, Fiber Distributed Data Interface(FDDI), RS232, IEEE 802.11, IEEE 802.11a, IEE 802.11b, IEEE 802.11g,IEEE 802.11n, WiMax and direct asynchronous connections, or anycombination and/or extensions thereof. The network may comprise mobiletelephone networks utilizing any protocol or protocols used tocommunicate among mobile devices, including AMPS, TDMA, CDMA, GSM, GPRSor UMTS.

FIGS. 2A and 2B depict block diagrams of a computing device 200 usefulfor practicing an embodiment of the computing devices illustrated inFIG. 1. Each may be deployed as and/or executed on any type and form ofcomputing device, such as a mobile platform, personal computer, server,network device, or appliance capable of communicating on any type andform of network and performing the operations described herein. As shownin FIGS. 2A and 2B, each computing device 200 includes a centralprocessing unit 221, and a main memory unit 222. As shown in FIG. 2A, acomputing device 200 may include one or more visual display devices 224a-n, a keyboard 226 and/or a pointing device 227, such as a mouse. Asshown in FIG. 2B, each computing device 200 may also include additionaloptional elements, such as one or more input/output devices 230 a-230 b(generally referred to using reference numeral 230), and a cache memory240 in communication with the central processing unit 221.

The central processing unit 221 is any logic circuitry that responds toand processes instructions fetched from the main memory unit 222. Inmany embodiments, the central processing unit is provided by amicroprocessor unit, such as: those manufactured by Intel Corporation ofMountain View, Calif.; those manufactured by Motorola Corporation ofSchaumburg, Ill.; those manufactured by Transmeta Corporation of SantaClara, Calif.; the RS/6000 processor, those manufactured byInternational Business Machines of White Plains, N.Y.; or thosemanufactured by Advanced Micro Devices of Sunnyvale, Calif. Thecomputing device 200 may be based on any of these processors, or anyother processor capable of operating as described herein. The centralprocessing unit 221 may be a single core or multi-core. The centralprocessing unit 221 may comprise one or more processors.

Main memory unit 222 may be one or more memory chips capable of storingdata and allowing any storage location to be directly accessed by themicroprocessor 221, such as Static random access memory (SRAM), BurstSRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM),Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended DataOutput RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), BurstExtended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM),synchronous DRAM (SDRAM), JEDEC SRAM, PC200 SDRAM, Double Data RateSDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM),Direct Rambus DRAM (DRDRAM), or Ferroelectric RAM (FRAM). The mainmemory 222 may be based on any of the above described memory chips, orany other available memory chips capable of operating as describedherein. In the embodiment shown in FIG. 2A, the processor 221communicates with main memory 222 via a system bus 250 (described inmore detail below). FIG. 2B depicts an embodiment of a computing device200 in which the processor communicates directly with main memory 222via a memory port 203. For example, in FIG. 2B the main memory 222 maybe DRDRAM.

FIG. 2B depicts an embodiment in which the main processor 221communicates directly with cache memory 240 via a secondary bus,sometimes referred to as a backside bus. In other embodiments, the mainprocessor 221 communicates with cache memory 240 using the system bus250. Cache memory 240 typically has a faster response time than mainmemory 222 and is typically provided by SRAM, BSRAM, or EDRAM. In theembodiment shown in FIG. 2B, the processor 221 communicates with variousI/O devices 230 via a local system bus 250. Various buses may be used toconnect the central processing unit 221 to any of the I/O devices 230,including a VESA VL bus, an ISA bus, an EISA bus, a MicroChannelArchitecture (MCA) bus, a PCI bus, a PCI-X bus, a PCI-Express bus, or aNuBus. For embodiments in which the I/O device is a video display 224,the processor 221 may use an Advanced Graphics Port (AGP) to communicatewith the display 224. FIG. 2B depicts an embodiment of a computer 200 inwhich the main processor 221 communicates directly with I/O device 230 bvia HyperTransport, Rapid I/O, or InfiniBand. FIG. 2B also depicts anembodiment in which local busses and direct communication are mixed: theprocessor 221 communicates with I/O device 230 a using a localinterconnect bus while communicating with I/O device 230 b directly.

The computing device 200 may support any suitable installation device216, such as a floppy disk drive for receiving floppy disks such as3.5-inch, 5.25-inch disks or ZIP disks, a CD-ROM drive, a CD-R/RW drive,a DVD-ROM drive, tape drives of various formats, USB device, hard-driveor any other device suitable for installing software and programs orportions thereof. The computing device 200 may further comprise astorage device, such as one or more hard disk drives or redundant arraysof independent disks, Flash memory, or EEPROMs, for storing an operatingsystem and other related software, and for storing application softwareprograms. Optionally, any of the installation devices 216 could also beused as the storage device. Additionally, the operating system and thesoftware can be run from a bootable medium, for example, a bootable CD,such as KNOPPIX®, a bootable CD for GNU/Linux that is available as aGNU/Linux distribution from knoppix.net.

Furthermore, the computing device 200 may include a network interface218 to interface to a Local Area Network (LAN), Wide Area Network (WAN)or the Internet through a variety of connections including, but notlimited to, standard telephone lines, LAN or WAN links (e.g., 802.11,T1, T3, 56 kb, X.25, SNA, DECNET), broadband connections (e.g., ISDN,Frame Relay, ATM, Gigabit Ethernet, Ethernet-over-SONET, ADSL, SDSL),wireless connections, or some combination of any or all of the above.Connections can be established using a variety of communicationprotocols. In one embodiment, the computing device 200 communicates withother computing devices 200 via any type and/or form of gateway ortunneling protocol such as Secure Socket Layer (SSL) or Transport LayerSecurity (TLS), or the Citrix Gateway Protocol manufactured by CitrixSystems, Inc. of Ft. Lauderdale, Fla. The network interface 218 maycomprise a built-in network adapter, network interface card, PCMCIAnetwork card, card bus network adapter, wireless network adapter, USBnetwork adapter, modem or any other device suitable for interfacing thecomputing device 200 to any type of network capable of communication andperforming the operations described herein.

A wide variety of I/O devices 230 a-230 n may be present in thecomputing device 200. Input devices include keyboards, mice, trackpads,trackballs, microphones, touch screens, and drawing tablets. Outputdevices include video displays, touch screens, speakers, inkjetprinters, laser printers, and dye-sublimation printers. The I/O devicesmay be controlled by an I/O controller 223 as shown in FIG. 2A. The I/Ocontroller may control one or more I/O devices such as a keyboard 226and a pointing device 227, e.g., a mouse or optical pen. Furthermore, anI/O device may also provide storage and/or an installation medium 216for the computing device 200. In still other embodiments, the computingdevice 200 may provide USB connections to receive handheld USB storagedevices such as the USB Flash Drive line of devices manufactured byTwintech Industry, Inc. of Los Alamitos, Calif.

In some embodiments, the computing device 200 may comprise or beconnected to multiple display devices 224 a-224 n, which each may be ofthe same or different type and/or form. As such, any of the I/O devices230 a-230 n and/or the I/O controller 223 may comprise any type and/orform of suitable hardware, software, or combination of hardware andsoftware to support, enable or provide for the connection and use ofmultiple display devices 224 a-224 n by the computing device 200. Forexample, the computing device 200 may include any type and/or form ofvideo adapter, video card, driver, and/or library to interface,communicate, connect or otherwise use the display devices 224 a-224 n.In one embodiment, a video adapter may comprise multiple connectors tointerface to multiple display devices 224 a-224 n. In other embodiments,the computing device 200 may include multiple video adapters, with eachvideo adapter connected to one or more of the display devices 224 a-224n. In some embodiments, any portion of the operating system of thecomputing device 200 may be configured for using multiple displays 224a-224 n. In other embodiments, one or more of the display devices 224a-224 n may be provided by one or more other computing devices, such ascomputing devices 200 a and 200 b connected to the computing device 200,for example, via a network. These embodiments may include any type ofsoftware designed and constructed to use another computer's displaydevice as a second display device 224 a for the computing device 200.One ordinarily skilled in the art will recognize and appreciate thevarious ways and embodiments that a computing device 200 may beconfigured to have multiple display devices 224 a-224 n.

In further embodiments, an I/O device 230 may be a bridge between thesystem bus 250 and an external communication bus, such as a USB bus, anApple Desktop Bus, an RS-232 serial connection, a SCSI bus, a FireWirebus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a GigabitEthernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a SuperHIPPI bus, a SerialPlus bus, a SCI/LAMP bus, a FibreChannel bus, or aSerial Attached small computer system interface bus.

A computing device 200 of the sort depicted in FIGS. 2A and 2B typicallyoperates under the control of operating systems, which controlscheduling of tasks and access to system resources. The computing device200 can be running any operating system such as any of the versions ofthe MICROSOFT WINDOWS operating systems, the different releases of theUnix and Linux operating systems, any version of the MAC OS forMacintosh computers, any embedded operating system, any real-timeoperating system, any open source operating system, any proprietaryoperating system, any operating systems for mobile computing devices, orany other operating system capable of running on the computing deviceand performing the operations described herein. Typical operatingsystems include: WINDOWS 3.x, WINDOWS 95, WINDOWS 98, WINDOWS 2000,WINDOWS NT 3.51, WINDOWS NT 4.0, WINDOWS CE, WINDOWS XP, and WINDOWSVISTA, all of which are manufactured by Microsoft Corporation ofRedmond, Wash.; MACOS, manufactured by Apple Computer of Cupertino,Calif.; OS/2, manufactured by International Business Machines of Armonk,N.Y.; and Linux, a freely-available operating system distributed byCaldera Corp. of Salt Lake City, Utah, or any type and/or form of a Unixoperating system, among others.

The computer system 200 can be any workstation, desktop computer, laptopor notebook computer, server, handheld computer, mobile telephone orother portable telecommunication device, media playing device, a gamingsystem, mobile computing device, or any other type and/or form ofcomputing, telecommunications or media device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. For example, thecomputer system 200 may comprise a device of the IPOD family of devicesmanufactured by Apple Computer of Cupertino, Calif., a PLAYSTATION 2,PLAYSTATION 3, or PERSONAL PLAYSTATION PORTABLE (PSP) devicemanufactured by the Sony Corporation of Tokyo, Japan, a NINTENDO DS,NINTENDO GAMEBOY, NINTENDO GAMEBOY ADVANCED or NINTENDO REVOLUTIONdevice manufactured by Nintendo Co., Ltd., of Kyoto, Japan, or an XBOXor XBOX 360 device manufactured by the Microsoft Corporation of Redmond,Wash.

For embodiments comprising mobile devices, the device may be aJAVA-enabled cellular telephone, such as the i55sr, i58sr, i85s, or thei88s, all of which are manufactured by Motorola Corp. of Schaumburg,Ill.; the 6035 or the 7135, manufactured by Kyocera of Kyoto, Japan; orthe i300 or i330, manufactured by Samsung Electronics Co., Ltd., ofSeoul, Korea. In other embodiments comprising mobile devices, a mobiledevice may be a personal digital assistant (PDA) operating under controlof the PalmOS operating system, such as the Tungsten W, the VII, theVIIx, the i705, all of which are manufactured by palmOne, Inc. ofMilpitas, Calif. In further embodiments, the client 102 may be apersonal digital assistant (PDA) operating under control of the PocketPCoperating system, such as the iPAQ 4155, iPAQ 5555, iPAQ 1945, iPAQ2215, and iPAQ 4255, all of which manufactured by Hewlett-PackardCorporation of Palo Alto, Calif.; the ViewSonic V36, manufactured byViewSonic of Walnut, Calif.; or the Toshiba PocketPC e405, manufacturedby Toshiba America, Inc. of New York, N.Y. In still other embodiments,the mobile device is a combination PDA/telephone device such as the Treo180, Treo 270, Treo 600, Treo 650, Treo 700, or the Treo 700w, all ofwhich are manufactured by palmOne, Inc. of Milpitas, Calif., or theIPHONE family of devices manufactured by Apple Computer. In stillfurther embodiments, the mobile device is a cellular telephone thatoperates under control of the PocketPC operating system, such as theMPx200, manufactured by Motorola Corp. In still other embodiments, amobile device may comprise a mobile gaming device with wirelesscommunication capability. A typical mobile device may comprise many ofthe elements described above in FIGS. 2A and 2B, including the processorand the main memory.

FIG. 3 is a flowchart for a method of facilitating management ofcloud-based service instances. In some embodiments, the method 300 isperformed by the cloud management service 110 or components responsivethereto. The manager 110 is configured to communicate with amulti-tenant computing cloud 120 a-z. At step 310, the manager 110establishes a cloud-based service instance 130 hosted in themulti-tenant computing cloud 120 a and an access entity with permissionsto access the established cloud service instance 130. At step 330, themanager 110 receives a request for the cloud-based service instance, therequest authenticated as originating from a requestor, e.g., customerdevice 115. At step 350, the manager 110 consults a set of accesscontrols associated with the cloud-based service instance and determinesif the request is allowable by the requestor. At step 370, the manager110 enables the requestor to complete the request using a restrictedaccess credential associated with the access entity.

At step 310, in more detail, the manager 110 establishes a cloud-basedservice instance 130 hosted in the multi-tenant computing cloud 120 aand an access entity with permissions to access the established cloudservice instance. In some embodiments, the access entity is establishedconcurrently with the cloud-based service instance. In some embodiments,a pre-existing access entity is granted permissions, or identified tohave sufficient permissions, to access a newly established cloud-basedservice instance. For example, the cloud-based service instance may begrouped together with other instances and a single access entity may begranted permissions to every instance in the group. The cloud-basedservice instance may participate in a resource pool comprising one ormore cloud-based service instances. A resource pool may also bedescribed as a collection of resources or a deployment. In someembodiments multiple access entities, e.g., for multiple requestors, areeach granted permissions to access the newly established cloud-basedservice instance. In some embodiments, a new access entity is createdwith permissions specific to the newly established cloud-based serviceinstance. A requestor may utilize multiple access entities. In someembodiments, an access entity's permissions are restricted to onlyaccessing cloud-based service instances in a particular resource pool.Credentials for a new access entity, e.g., an access identity name andpassword, may be set by the manager 110 or the cloud controller 124. Insome embodiments, the manager provides an access identity name and thehost generates a new password, which the manager stores in associationwith the identity name. In other embodiments, credentials for a newaccess entity consist of a private/public key pair or a key identifierand a cryptographic key.

In some embodiments, the manager 110 establishes the cloud-based serviceinstance 130 by communicating with the multi-tenant computing cloud 120a. For example, the manager 110 may submit instructions to create,start, instantiate, discover, identify, duplicate, import, configure, orgenerate, the cloud-based service instance. The instructions may bereceived by a server or service operated by the cloud host. In someembodiments, the manager 110 submits a single instruction. In someembodiments, the manager 110 submits multiple instructions. For example,the manager 110 may establish an access entity separately fromestablishing the cloud-based service instance. The instructions may besubmitted using an application programming interface (API) specific tothe cloud or cloud provider. In some embodiments, multiple accessentities are created for a cloud-based service instance.

Examples of the cloud-based services include a service providing adatabase, a load balancer, a message queue, a communication channel, ordata storage. For example, Amazon.com, Inc., provides the Amazon SimpleStorage Service (Amazon S3), Amazon Elastic Load Balancing service(Amazon ELB), and Amazon Relational Database Service (Amazon RDS). Somecloud-based service instances may interact with other cloud-basedservice instances. For example, Amazon.com, Inc., provides the AmazonElastic Load Balancer (Amazon ELB), which automatically distributesincoming application traffic across multiple virtual server instances inthe Amazon Elastic Compute Cloud (Amazon EC2). The manager 110 mayestablish multiple Amazon EC2 instances and an Amazon ELB instance toload balance the EC2 instances. Each instance may be established with aninstance-specific access entity. In some embodiments, the cloud-basedservice instance is a virtual service provided in the multi-tenantcomputing cloud. For example, the service may be provided by a server,or virtual server, operated by the cloud host and these servers aretypically hidden from the user behind the service's interface. In someembodiments, a service may be exposed as if it were a virtual serversthat can be accessed individually. For example, Amazon Elastic MapReduce (EMR), may be exposed as a server even though it is a service.

At step 330, the manager 110 receives a request for the cloud-basedservice instance, the request authenticated as originating from arequestor. The request may be described as an authenticated requestbecause the origin of the request can be authenticated as coming from arequestor known to, or previously authenticated by, the manager 110. Insome embodiments, the request is authenticated or verified by themanager 110. In some embodiments, the authenticity of the request fromthe requestor is verified using a cryptographic signature. Theauthenticated request may be cryptographically signed by one or more ofthe requestor, an authentication service, and a third-party signingauthority. In some embodiments, the manager 110 uses a key to decryptthe message, a hash value associated with the message, or a signaturetoken accompanying the message. In some embodiments, the message isauthenticated by virtue of arriving via a secured trusted channel, e.g.,on a private network.

There are several known techniques for signing a message. The entiremessage may be encrypted or the message may be processed using a hashfunction to generate a short digest (“hash value”) that may then beencrypted and bundled with the original message. In some embodiments, asender obtains a certificate from a trusted thirty party for use inauthentication. The certificate generally includes an identifier for thesender and a public key for the sender. The certificate may also includeadditional information such as a date stamp. The certificate, or a hashvalue of the certificate, may be encrypted using a private keycontrolled by the third party as evidence that the certificate wasissued by the third party. The sender encrypts the message, or a hashvalue of the message, using a private key controlled by the sender andcorresponding to the public key in the certificate. A recipient of theencrypted message or hash value, possessing the certificate, can verifythe certificate with the trusted third-party and can use the public keyincluded in the certificate to verify that the message was sent by theparty identified in the certificate. The certificate need not be sentwith every message. For example, the certificate may have a period ofpresumed validity based on the date stamp. Other methods ofauthenticating the source of a message can also be used, such as aone-time key, a challenge-response exchange, or participation in a trustnetwork.

At step 350, the manager 110 consults a set of access controlsassociated with the cloud-based service instance and determines if therequest is allowable by the requestor. The cloud-based service instanceis associated with a set of access controls, e.g., an access controllist. The access controls indicate if the requestor of an authenticatedrequest is authorized to make the request. The manager 110 determines ifthe request is authorized. For example, a requestor may be authorized tocollect statistics or perform read-only operations but not to makechanges. If a request is both authenticated and authorized then themanager 110 will facilitate the request. The access controls may bestored by the manager 110. The access controls may be stored in adatabase or data storage system accessible by the manager 110, e.g.,over a network. The access controls may be structured in a hierarchy.Each cloud-based service instance may have a set of access controlsspecific to the respective instance. Cloud-based service instances maybe grouped together (for example into a “deployment”) and have a singleset of access controls for the group.

A request received by the manager 110 may be a request to collectmonitoring data, configure or modify settings, read data, write data,perform a query, en-queue or de-queue a message, apply settings from abatch or script, upload or run a script, execute custom code, establisha service, duplicate a server, associate a service instance with aresource pool, group service instances into a resource pool, pause aservice, terminate a service or server, or any other request thatimpacts a cloud-based server or service instance.

At step 370, the manager 110 enables the requestor to complete therequest using an access credential associated with an access entity. Insome embodiments, the access entity may be identified by the requestor.In some embodiments, the access entity may be selected by the manager110. The access entity may be selected based on the identity of therequestor. The access entity may be based on the nature of the request.For example, an access entity with fewer rights or privileges may beused where the request does not require more substantial rights. Thatis, a request to retrieve data does not necessarily require an accessentity with administrative rights and the manager 110 may therefore usea non-administrative access entity. The access entity may be selectedbased on the virtual servers or services to be accessed by the request.For example, an access entity that only has rights to access a singleserver might be used for access to that server, where no other access isneeded. Thus the access entity may be selected by the manager 110 thatbest suits the requirements of the request.

In some embodiments, the manager 110 may create a new access entity witha new access credential and configure the access entity's permissions inthe multi-tenant compute cloud such that the access entity only hasaccess to the cloud-based virtual servers and/or cloud-based serviceinstances being accessed in the request. The access entity may becreated to narrowly enable the requestor to perform the request whilenot providing the requestor any access not necessary to the request. Thenew access entity may be disabled or deleted upon completion of therequest. The new access entity may be disabled or deleted after a periodof time has passed.

The manager 110 only enables a request that originated with a verifiedrequestor authorized to make the request. In some embodiments, themanager passes the authenticated authorized request to the cloud host orcloud-based service instance. The manager may convert the request from afirst request language or format into a second request language orformat tailored to the destination cloud-based service instance or cloudhost. In some embodiments, the manager 110 performs the authenticatedauthorized request. In some embodiments, the manager 110 returns a tokenor credential to the requestor, enabling the requestor to communicatedirectly with the cloud-based service instance to complete the request.The token may be a single use or one-time credential. In someembodiments, the manager 110 subsequently alters the credential, e.g.,changes the password, to terminate or revoke a credential returned tothe requestor. The manager 110 may revoke the credential after a fixedperiod of time, i.e., the credential may expire. The manager 110 mayrevoke the credential responsive to a completion event indicating thatthe requestor is no longer using the credential.

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments of the subject matterdescribed in this specification can be implemented as one or morecomputer programs, i.e., one or more modules of computer programinstructions, encoded on computer-readable storage media for executionby, or to control the operation of, data processing apparatus. Theprogram instructions can be encoded on an artificially generatedpropagated signal, e.g., a machine-generated electrical, optical, orelectromagnetic signal that is generated to encode information fortransmission to suitable receiver apparatus for execution by a dataprocessing apparatus. A computer-readable storage medium can be, or beincluded in, a computer-readable storage device, a computer-readablestorage substrate, a random or serial access memory array or device, ora combination of one or more of them. Moreover, while acomputer-readable storage medium is not a propagated signal, acomputer-readable storage medium can be a source or destination ofcomputer program instructions encoded in an artificially generatedpropagated signal. The computer-readable storage medium can also be, orbe included in, one or more separate physical components or media (e.g.,multiple DVDs, CDs, disks, or other storage devices).

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources. The term “data processing apparatus” or “computing device”encompasses all kinds of apparatus, devices, and machines for processingdata, including by way of example a programmable processor, a computer,a system on a chip, or multiple ones, or combinations, of the foregoing.The apparatus can include special purpose logic circuitry, e.g., an FPGA(field programmable gate array) or an ASIC (application specificintegrated circuit). The apparatus can also include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures. Thesystems described can include or share one or more data processingapparatuses, computing devices, or processors.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), for example. Devicessuitable for storing computer program instructions and data include allforms of non volatile memory, media and memory devices, including by wayof example semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD-ROM disks. Theprocessor and the memory can be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a LCD (liquid crystal display) monitor,LED or OLED screen, a CRT (cathode ray tube), a plasma screen, or aprojector, for displaying information to the user and a touch screen,keyboard, or a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front end component, e.g., aclient computer having a graphical user interface or a web browserthrough which a user can interact with an embodiment of the subjectmatter described in this specification, or any combination of one ormore such back end, middleware, or front end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing systems described can include clients and servers. Aclient and server are generally remote from each other and typicallyinteract through a communication network. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

While this specification contains many specific embodiment details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features described in this specification in the context ofseparate embodiments can also be implemented in combination in a singleembodiment. Conversely, various features described in the context of asingle embodiment can also be implemented in multiple embodimentsseparately or in any suitable sub-combination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination can in some cases be excised from the combination, and theclaimed combination may be directed to a sub-combination or variation ofa sub-combination. Similarly, while operations are depicted in thedrawings in a particular order, this should not be understood asrequiring that such operations be performed in the particular ordershown or in sequential order, or that all illustrated operations beperformed, to achieve desirable results. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the embodiments describedabove should not be understood as requiring such separation in allembodiments, and it should be understood that the described programcomponents and systems can generally be integrated in a single softwareproduct or packaged into multiple software products.

Where technical features in the drawings, detailed description or anyclaim are followed by reference signs, the reference signs have beenincluded for the sole purpose of increasing the intelligibility of thedrawings, detailed description, and claims. Accordingly, neither thereference signs nor their absence have any limiting effect on the scopeof any claim elements. References to “or” may be construed as inclusiveso that any terms described using “or” may indicate any of a single,more than one, and all of the described terms.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims.

The invention claimed is:
 1. A method of facilitating management of cloud-based service instances, the method comprising: establishing, by a cloud management service configured to communicate with a multi-tenant computing cloud, a cloud-based service instance hosted in the multi-tenant computing cloud and an access entity with permissions to access the established cloud-based service instance; receiving, by the cloud management service, a request for the cloud-based service instance, the request authenticated as originating from a requestor, wherein the request is a request for direct access, by the requestor, to the cloud-based service instance; consulting, by the cloud management service, a set of access controls associated with the cloud-based service instance; determining, by the cloud management service, responsive to the consulting, if the request is allowable by the requestor; and enabling, by the cloud management service responsive to determining that the request is allowable by the requestor, the requestor to complete the request using an access credential associated with the access entity by returning, to the requestor, the access credential associated with the access entity.
 2. The method of claim 1, wherein establishing the cloud-based service instance comprises communicating, by the cloud management service, with the multi-tenant computing cloud, to create, start, instantiate, discover, identify, duplicate, import, configure, or generate, the cloud-based service instance.
 3. The method of claim 1, wherein the cloud-based service instance provides one of a database, a load balancer, a message queue, a communication channel, and data storage.
 4. The method of claim 1, wherein the cloud-based service instance is a virtual service provided in the multi-tenant computing cloud.
 5. The method of claim 1, wherein the access entity permissions are restricted to allow access only to the established cloud service instance.
 6. The method of claim 1, wherein the cloud-based service instance is associated with a resource pool comprising one or more cloud-based service instances and the access entity permissions are restricted to only accessing cloud-based service instances in the resource pool.
 7. The method of claim 1, further comprising establishing, by the cloud management service, responsive to determining that the request is allowable by the requestor, a custom access entity with permissions sufficient to perform the request, wherein enabling the requestor to complete the request comprises enabling the requestor to complete the request using an access credential associated with the custom access entity.
 8. The method of claim 1, wherein establishing further comprises storing, by the cloud management service, the access credential for the access entity.
 9. A method of facilitating management of cloud-based service instances, the method comprising: establishing, by a cloud management service configured to communicate with a multi-tenant computing cloud, a cloud-based service instance hosted in the multi-tenant computing cloud and an access entity with permissions to access the established cloud-based service instance; receiving, by the cloud management service, a request for the cloud-based service instance, the request authenticated as originating from a requestor, wherein the request is a request to perform an action on the cloud-based service instance; consulting, by the cloud management service, a set of access controls associated with the cloud-based service instance; determining, by the cloud management service, responsive to the consulting, if the request is allowable by the requestor; and enabling, by the cloud management service responsive to determining that the request is allowable by the requestor, the requestor to complete the request using an access credential associated with the access entity by forwarding the request to the multi-tenant computing cloud, with the access credential associated with the access entity.
 10. The method of claim 9, wherein establishing the cloud-based service instance comprises communicating, by the cloud management service, with the multi-tenant computing cloud, to create, start, instantiate, discover, identify, duplicate, import, configure, or generate, the cloud-based service instance.
 11. The method of claim 9, wherein the cloud-based service instance provides one of a database, a load balancer, a message queue, a communication channel, and data storage.
 12. The method of claim 9, wherein the cloud-based service instance is a virtual service provided in the multi-tenant computing cloud.
 13. The method of claim 9, wherein the access entity permissions are restricted to allow access only to the established cloud service instance.
 14. The method of claim 9, wherein the cloud-based service instance is associated with a resource pool comprising one or more cloud-based service instances and the access entity permissions are restricted to only accessing cloud-based service instances in the resource pool.
 15. The method of claim 9, further comprising establishing, by the cloud management service, responsive to determining that the request is allowable by the requestor, a custom access entity with permissions sufficient to perform the request, wherein enabling the requestor to complete the request comprises enabling the requestor to complete the request using an access credential associated with the custom access entity.
 16. The method of claim 9, wherein establishing further comprises storing, by the cloud management service, the access credential for the access entity.
 17. A system for facilitating management of cloud-based service instances, the system comprising one or more servers including one or more hardware processors configured to communicate with at least one multi-tenant computing cloud, the one or more servers including one or more hardware processors configured to: establish a cloud-based service instance hosted in the multi-tenant computing cloud and an access entity with permissions to access the established cloud-based service instance; receive a request for the cloud-based service instance, the request authenticated as originating from a requestor, wherein the request is a request for direct access, by the requestor, to the cloud-based service instance; consult a set of access controls associated with the cloud-based service instance; determine, responsive to the consulting, if the request is allowable by the requestor; and enable, responsive to determining that the request is allowable by the requestor, the requestor to complete the request using a access credential associated with the access entity by returning, to the requestor, the access credential associated with the access entity.
 18. The system of claim 17, wherein the one or more servers including one or more hardware processors is further configured to establish the cloud-based service instance by communicating with the multi-tenant computing cloud to create, start, instantiate, discover, identify, duplicate, import, configure, or generate, the cloud-based service instance.
 19. The system of claim 17, wherein the cloud-based service instance provides one of a database, a load balancer, a message queue, a communication channel, and data storage.
 20. The system of claim 17, wherein the cloud-based service instance is a virtual service provided in the multi-tenant computing cloud.
 21. The system of claim 17, wherein the access entity permissions are restricted to allow access only to the established cloud service instance.
 22. The system of claim 17, wherein the cloud-based service instance is associated with a resource pool comprising one or more cloud-based service instances and the access entity permissions are restricted to only accessing cloud-based service instances in the resource pool.
 23. The system of claim 17, wherein the one or more servers including one or more hardware processors is further configured to establish, responsive to determining that the request is allowable by the requestor, a custom access entity with permissions sufficient to perform the request; and wherein the one or more servers including one or more hardware processors is configured to enable the requestor to complete the request using an access credential associated with the custom access entity.
 24. The system of claim 17, wherein the one or more servers including one or more hardware processors is further configured to store the access credential for the access entity.
 25. A system for facilitating management of cloud-based service instances, the system comprising one or more servers including one or more hardware processors configured to communicate with at least one multi-tenant computing cloud, the one or more servers including one or more hardware processors configured to: establish a cloud-based service instance hosted in the multi-tenant computing cloud and an access entity with permissions to access the established cloud-based service instance; receive a request for the cloud-based service instance, the request authenticated as originating from a requestor, wherein the request is a request to perform an action on the cloud-based service instance; consult a set of access controls associated with the cloud-based service instance; determine, responsive to the consulting, if the request is allowable by the requestor; and enable, responsive to determining that the request is allowable by the requestor, the requestor to complete the request using an access credential associated with the access entity by forwarding the request to the multi-tenant computing cloud with the access credential associated with the access entity.
 26. The system of claim 25, wherein the one or more servers including one or more hardware processors is further configured to establish the cloud-based service instance by communicating with the multi-tenant computing cloud to create, start, instantiate, discover, identify, duplicate, import, configure, or generate, the cloud-based service instance.
 27. The system of claim 25, wherein the access entity permissions are restricted to allow access only to the established cloud service instance.
 28. The system of claim 25, wherein the cloud-based service instance is associated with a resource pool comprising one or more cloud-based service instances and the access entity permissions are restricted to only accessing cloud-based service instances in the resource pool.
 29. The system of claim 25, wherein the one or more servers including one or more hardware processors is further configured to establish, responsive to determining that the request is allowable by the requestor, a custom access entity with permissions sufficient to perform the request; and wherein the one or more servers including one or more hardware processors is configured to enable the requestor to complete the request using an access credential associated with the custom access entity.
 30. The system of claim 25, wherein the one or more servers including one or more hardware processors is further configured to store the access credential for the access entity. 